Preparation Tasks

Before you can begin with the migration, there are some preparation tasks that need to be performed.

Preparation Process Table

Task Purpose
Sign Up Gain access to the destination environment.
Setup Destination Environment Prepare the vCD layout and network before the migration.
Create an API User Authenticate yourself for the migration.
Share vApps with Everyone in the Organization Make your servers visible to the migration tool.
Initiate the Migration Request Attach the migration storage to your servers.
Verify the migration storage profile Ensure that the migration storage is visible to both environments.
Technical Considerations Analyze your setup & take appropriate measures before migrating.

DCS+: Sign Up

First of all, you need to have a DCS+ account. You can get one by signing up on the DCS+ Order Page.

Note: You will receive a contract number (PRO-XXXXXXXX) for your new DCS+ environment. Usually, this will be the same number as for your regular DCS Classic service. Going forward, this contract number will also be referred to as "Business Group".

DCS+: Setup Destination Environment

Next, you need to make sure that the destination environment within DCS+ is properly prepared. We recommend the following steps:

  1. Order destination DDCs & external connectivity (internet access, WAN connectivity, etc.) in the DCS+ portal.
  2. In vCD, prepare/recreate your desired virtual network structure (IONs/EONs).
  3. Create destination vApp structure and attach all needed networks to the vApp.
  4. Verify if connectivity is working in general by provisioning an test VM and ensure that all needed services can be reached.
  5. (Optional) Copy your vCD media items (vApp templates, ISO files, etc.) to a new catalogue on DCS+.
  6. (Optional) Copy any VM description in vCD to a temporary location. These will be lost during the migration and need to be applied manually again.

    Preparation Tasks - 1

  7. (Optional) Take note of your local admin/root passwords from vCD. The information will be lost on migration, but the old password remains valid.

    Preparation Tasks - 2

DCS Classic: Create an API User

This user is required for authentication purposes and for moving the servers to the new environment. If you already have an API user, skip to point 5.

  1. Navigate to the DCS Classic portal
  2. Under "Dynamic Data Centers", click on "vCloud Director API"

    Create API User - 1

  3. If the list is empty, click on "Create new API user" on the bottom right.

    Create API User - 2

  4. Fill in the form and click "Submit Order". You can choose any username you like. This will create a service request, which may take a few minutes to complete.

    Create API User - 3

  5. Back on the overview screen, take note of the vOrg name and the login credentials of your API user. They will be required in an upcoming step.

DCS Classic: Share vApps with Everyone in the Organization

Finally, for the migration tool to see your vApps and move your servers, you'll need to share them with everyone within your organization. This is needed if you want to migrate a 'Dynamic Data Center', but not for 'Dynamic Server'.

  1. Open vCD.
  2. Click on vApps and hit "Share…" on the respective vApp.

    Share vApp - 1

  3. Select "Add Members" and then "Everyone in the Organization". Confirm with OK.

    Share vApp - 2

DCS+: Initiate the Migration Request

  1. Select the "Catalog" ribbon in the top navigation menu.
  2. On the left-hand side, click on "Service Requests".
  3. Choose the DCS+ target Business Group, where you would like to migrate your workload to. For this, simply click on the "Business Groups" field and select the appropriate contract number (PRO-XXXXXXXX) from the drop-down menu.
  4. Click the "Migration" field.

    Request Migration 1

  5. Read the description & accept the terms by clicking on "Request".

    Request Migration 2

  6. Fill in the contract & user credentials

    • Contract ID: This is the contract of the destination business group in DCS+ (PRO Number) – it should already be selected automatically, no change is needed here.
    • vOrg Name: The name of the virtual organization of the source platform (DCS Classic) that needs to be migrated. You can find this in the API user screen in DCS Classic.
    • API Username: The username of the API user – see chapter above.
    • API Password: The password used for the API user above.

      Note: The login credentials are necessary to validate your access authorization to this vOrg. It will not be used further by Swisscom afterwards.

      Request Migration 3

  7. If the credentials are accepted, you can click the Request button on the bottom right. The platform will now attach the migration storage profile to your DCS Classic and DCS+ IaaS environments.

Note: This process may take several minutes to complete, depending on the amount of DDCs in your environment.

DCS+: Verify the Migration Storage Profile

To verify that the migration request was successful, please check that the migration storage profile has been attached properly to the destination environment in DCS+.

  1. Login to the DCS+ portal.
  2. Open the vCD GUI by clicking the vCD button at the top right.

    Verify Storage Profile - 1

  3. Choose the "Business Group" that you have selected as the target destination before and click "Go".

  4. On the vCD landing page, click on the "Administration" ribbon.
  5. On the left-hand side, under the "Cloud Resources" tab, click "Virtual Datacenters".
  6. Double-click the destination vOrg, where you will migrate your servers to.

    Verify Storage Profile - 2

  7. Click on the "Storage Policies" tab. Here, you should now see that the destination vOrgs all have the migration storage available.

    Verify Storage Profile - 3

DCS Classic: Verify the Migration Storage Profile

Now perform the same steps again for the DCS Classic environment.

Technical Considerations

Before migrating to DCS+, there are some further aspects that you must consider beforehand.

Snapshot Backups
Existing snapshots on DCS Classic are not migrated to DCS+. If you need to perform a restore within 30 days after the migration, restore a snapshot on the DCS Classic portal and then migrate the data from there. Keep your DDCs & vDCs in DCS Classic for at least 30 days after the migration.
Swisscom performs an hourly snapshot of the data residing on the migration storage. Your data is kept safe during the migration.
At this point, you don't have the ability to perform a self-service restore from the DCS+ portal. In DCS+, you can initiate a restore request by contacting the regular service desk.
Existing manual snapshot created in vCD can not be migrated to DCS+. Delete your manual snapshots before relocation.
Public IPs will change after the migration due to the new product model. Depending on your setup, implement measures so that your service is still reachable via the old IP in case of having the addresses hard-coded in the configuration (e.g. HTTP proxy, NAT, redirection, etc.).
A new MAC address is being generated for your NICs after the migration. Verify if there are any hard-coded entries related to your MAC address (e.g. firewall license configuration).
Migration Process
Your VMs will be powered off during the migration. Shut down your servers gracefully before initiating the workload migration. If you have VMs that might not be able to handle a restart, duplicate the respective VMs by copying them into another vApp or vDC. That way you can perform a test migration of these copied servers beforehand.`
The tool creates one vApp per VM in DCS+. The original vCD vApp layout won't be transferred from DCS Classic directly. Create the destination vApp layout incl. connectivity beforehand. After the migration, move the VMs to their destination vApp afterwards.
Virtual Machine & vApp Configuration
Avoid special characters in the names of your vApps & VMs. Verify that the names of your VMs and vApps don't include non-standard characters such as umlauts (ö, ä, ü, ...), accents (é, à, ô, ...), or other special characters ($, !, ?, ...). Also, please avoid spaces (sp[ ]ace).
Virtual Machine Hardware Version. Please ensure that your 'virtual hardware version' is at least on version 10.
Detach ISO Files from VMs. Eject any ISO Files still attached to a VM before starting the migration process.

results matching ""

    No results matching ""